MuleSoft Accelerator for SAP

Allows you to reduce errors and manual intervention, and avoid the hassle of sending paper invoices by utilizing EDI messaging.

Contents

• Use case description
• Glossary
• High-level architecture
• Sequence diagram
• Use case considerations
• Systems involved
• Goals
• Assumptions and constraints
• Workflow
• Successful outcome

See also

• Downloadable assets

Overview

Across every industry from manufacturing to healthcare and retail, the streamlined B2B integration of your ERP systems (especially SAP) with those of your trading partners (buyers) is critical to your organization’s success.

MuleSoft Accelerator for SAP allows you to reduce errors and manual intervention, and avoid the hassle of sending paper invoices by utilizing EDI messaging. The solution leverages Anypoint Partner Manager to automate the full lifecycle of a typical order-to-cash workflow by integrating EDI transaction exchanges with you and your buyers and automatically creating an order back in SAP S/4HANA.

Use case description

The purpose of this use case is to enable the purchase order and post-purchase order transaction flows between businesses, with one business serving as the buyer and the other as the supplier. This is to support the inclusion of EDI message formats as a form of communication between applications.

Glossary

High-level architecture

Sequence diagram

Use case considerations

In order to use the pre-built EDI templates, suppliers would need to purchase the Anypoint Partner Manager add-on along with the EDI connector (X12). Buyers may use any EDI software of their choice.

• ANSI ASC X12 is the EDI document standard considered for this use case.
• The following EDI formats are supported in this use case:
  • EDI 850 : Purchase Order
  • EDI 855 : Purchase Order Acknowledgement
  • EDI 856 : Advanced Shipping Notice
  • EDI 810 : Invoice
  • EDI 820 : Payment Order/Remittance Advice

Technical considerations

• An SFTP server is set up to simulate a Buyer system.
• Buyer’s ERP would drop/pickup EDI files from the SFTP server.
• SAP S/4HANA is the Supplier system.
• The customer and the products used in EDI transactions are pre-synced between the Buyer and SAP S/4HANA.
• Use CIM as the canonical model where applicable.

End-to-end scenarios

• Purchase Order Transaction Flow:
  • 850 Purchase Order from Buyer to SAP S/4 HANA.
  • 855 Purchase Order Acknowledgment from SAP S/4 HANA to the Buyer.
• Post Purchase Order Transaction Flow:
  • 856 Advanced Shipping Notice from SAP S/4 HANA to the Buyer.
  • 810 Invoice from SAP S/4 HANA to the Buyer.
  • 820 Payment Order/Remittance Advice from Buyer to SAP S/4 HANA.

Systems involved

• B2B
• EDI
• SAP S/4HANA

Goals

The goal of the B2B/EDI use case is to support the:

• EDI transaction flows related to purchase orders and post-purchase orders between a Buyer and Supplier system.
• orchestration in Anypoint Partner Manager to receive the Purchase Order from the Buyer system and the creation of Sales Order in SAP S/4HANA.
• orchestration in Anypoint Partner Manager to receive the Purchase Order Acknowledgement from SAP S/4HANA and convert it to EDI 855 PO ACK.
• orchestration in Anypoint Partner Manager to receive the Advanced Shipping Notice from SAP S/4HANA and convert it to EDI 856 to send it to the Buyer.
• orchestration in Anypoint Partner Manager to receive the Invoice from SAP S/4HANA and convert it to EDI 810 to send it to the Buyer.
• orchestration in Anypoint Partner Manager to receive the remittance from the Buyer in the EDI 820 format to send it to the Supplier.

Assumptions and constraints

The following will be used to guide or constrain the solution design at a high level:

• The Cloud Information Model (CIM) will be used as the canonical model for inbound messages (order creation/remittance notice).
• For the purpose of this use case, an SFTP server is set up to simulate a Buyer system.

---

back to top

Before you begin

The Accelerators setup guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications.

Workflow

This use case enables EDI transactions between Buyer and the Supplier for the Purchase Order Flow.

Goal

To allow a Bi-directional communication between the Buyer and the Supplier for the Purchase Order and Post Purchase Order Transaction Flow.

Steps

1. An EDI Purchase Order (850) file is placed in the SFTP server (Buyer).
2. In APM, an Inbound Message Flow for the Buyer is created to:
   • Receive the EDI 850 PO from the SFTP server (Buyer)
   • Convert the EDI 850 PO to Order CIM
   • Send the order creation request to SAP S/4 HANA
3. SAP S/4 HANA sends back a Purchase Order Acknowledgement, Advanced Shipping Notice, and Invoice Notice in a SOAP message format to SAP Event Listener.
4. The SAP Event Listener converts the SOAP message to JSON with required EDI properties.
5. In APM, an Outbound Message Flow to the Buyer is configured to:
   1. Receive the JSON message from the SAP Event Listener
   2. Convert the JSON message to the appropriate EDI format: EDI 855 (PO ACK), EDI 856 (Advanced Shipping Notice), or EDI 810 (Invoice)
   3. Send the corresponding EDI message to the SFTP server (Buyer)

Successful outcome

• Creation of Sales Order in SAP S/4 HANA.
• Creation of EDI 855 PO ACK and sent to the SFTP server (Buyer).
• Creation of EDI 856 Advanced Shipping Notice and sent to the SFTP server (Buyer)
• Creation of EDI 810 Invoice and sent to the SFTP server (Buyer)
• Creation of Invoice payment in SAP S/4 HANA.

Downloadable assets

System APIs

• SAP S/4HANA Invoice Payments System API | API Specification | Implementation Template
• SAP S/4HANA Orders System API | API Specification | Implementation Template

Listeners

• SAP Event Listener | Implementation Template

Custom components

• SAP EDI APM Translation Maps | Source

---

back to top